JCapper Message Board

JCapper 101
-- Data Window/UDM Development

Home	Register Log In

Data Window/UDM Development

SILVER01HDW
12/19/2015
2:16:54 AM

So I have a pretty good UDM going here, but I'd like to toss out one factor. Can I do it?

Wins 23 27 33
Plays 59 59 59
PCT .3898 .4576 .5593

ROI 2.6458 1.3254 1.0322
Avg Mut 13.57 5.79 3.69

By: AFR

>=Min < Max Gain Bet Roi Wins Plays Pct Impact
-999.00 15.00 0.00 0.00 0.0000 0 0 .0000 0.0000
15.00 20.00 0.00 0.00 0.0000 0 0 .0000 0.0000
20.00 25.00 0.00 0.00 0.0000 0 0 .0000 0.0000
25.00 30.00 0.00 0.00 0.0000 0 0 .0000 0.0000
30.00 35.00 0.00 0.00 0.0000 0 0 .0000 0.0000
35.00 40.00 0.00 0.00 0.0000 0 0 .0000 0.0000
40.00 45.00 0.00 0.00 0.0000 0 0 .0000 0.0000
45.00 50.00 0.00 0.00 0.0000 0 0 .0000 0.0000
50.00 55.00 0.00 0.00 0.0000 0 0 .0000 0.0000
55.00 60.00 0.00 0.00 0.0000 0 0 .0000 0.0000
60.00 65.00 101.60 10.00 11.1600 2 5 .4000 1.0261
65.00 70.00 19.40 14.00 2.3857 3 7 .4286 1.0994
70.00 75.00 9.20 18.00 1.5111 2 9 .2222 0.5700
75.00 80.00 42.80 24.00 2.7833 5 12 .4167 1.0688
80.00 85.00 11.40 14.00 1.8143 4 7 .5714 1.4658

85.00 90.00 -9.60 20.00 0.5200 2 10 .2000 0.5130

90.00 95.00 25.40 12.00 3.1167 5 6 .8333 2.1377
95.00 100.00 -6.00 6.00 0.0000 0 3 .0000 0.0000

In this case, I'd like to set a range for AFR for 60-85 and 90-95. Is there a way I can do that in the UDM wizard to toss out the low percentage 85-90 range in this particular UDM?

jeff
12/19/2015
10:16:53 AM

--quote:

"...In this case, I'd like to set a range for AFR for 60-85 and 90-95. Is there a way I can do that in the UDM wizard to toss out the low percentage 85-90 range in this particular UDM?"

--end quote

Playlist File Mode:
If you are operating the program in playlist file mode:

Your best strategy is to use two separate UDMs. Both UDMs are identical except for the following:

1. The first UDM has an AFR min val of 60 and an AFR max val of 84.999 (or 85 depending on where you really want your cutoff to be.)

2. The second UDM has an AFR min val of 90 and an AFR max val of 94.999 (or 95 depending on where you really want your cutoff to be.)

Hint: Create the first UDM. Then use the CLONE button in the UDM Wizard to create the second UDM. From there, bring up the second UDM in the UDM Wizard and modify its factor constraints for AFR.

SQL Mode:
You have a lot more flexibility if you are operating the program in sql mode.

You can embed multiple factor constraints into a SQL UDM Definition for any of the data fields in the StarterHistory table including the F-slot number AFR is assigned to in your SQL Factor Setup. (Link to a 4 part web tutorial for editing the SQL Factor Setup.)

Suppose for the sake of argument that AFR is assigned to slot number F01 in your SQL Factor Setup.

If that's the case you could define multiple ranges for AFR in a SQL UDM Definition as follows:

AND ((VALF01 >= 60 AND VALF01 < 85) OR ((VALF01 >= 90 AND VALF01 < 95))

Notes:

• Placement of parenthesis characters in the above example is crucial.

• The db driver is programmed to evaluate valid sql text (even sql text defining many factor constraints) wrapped inside of parenthesis characters as if it were a single factor constraint.

• Therefore: the above sql code actually gets evaluated by the db driver as follows:

AND ((A) OR ((B))

Note:

• In the above line of sql (A) = "VALF01 >= 60 AND VALF01 < 85" (without the quotes) and (B) = "VALF01 >= 90 AND VALF01 < 95" (again without the quotes.) At least that's how the db driver evaluates it.

Alternately, if you are operating in sql mode, you could simply exclude the AFR range that you don't want.

Example:

AND NOT (VALF01 BETWEEN 85 AND 90)

Note:

• Again, placement of the parenthesis characters is crucial.

-jp

.

SILVER01HDW
12/19/2015
10:40:45 AM

Thanks, Jeff

jeff
12/19/2015
10:42:31 AM

One additional thought:

Something like 2 wins from 10 plays is not enough data (for me) to want to add factor constraints to a UDM based on the middle rows of a data breakout displayed in the Data Window.

I'd want to see a larger sample before doing that.

Generally, I find that excluding data at the edges (meaning rows near the bottom or the top) of a data breakout displayed in the Data Window tends to help improve UDM performance going forward in time.

For most of the UDMs I create I very rarely get improved performance by excluding rows from the middle of a sample - the primary exception being when those middle rows represent inside or outside path bias (for example when the rows in my Data Window results are for RailPosition at a specific track-intsurface-dist course layout configuration.)

-jp

.

SILVER01HDW
12/19/2015
2:04:22 PM

That's very honest and straightforward. I've decided to leave it alone and see where it goes. Starting to get comfortable with the program and UDM creation.

JCapper Message Board

JCapper 101 -- Data Window/UDM Development

JCapper 101
-- Data Window/UDM Development